I/O bound
英
美
输入输出界限
双语例句
- The basics involve ensuring an adequate number of physical disks to keep the system from becoming I/ O bound.
首先，要确保有足够的物理磁盘，以避免系统成为I/O密集型系统。 - Besides the physical disk, pay close attention to "Wait"( in the CPU section up top), which also helps determine if the system is I/ O bound.
除了物理磁盘之外，请仔细观察“Wait”（在CPU部分的上部），它也可以帮助确定系统是不是I/O绑定的。 - Compressing XML data and XML indexes can improve storage efficiency and runtime performance of queries that are I/ O bound.
压缩XML数据和XML索引可以提高存储效率和受I/O限制的查询的运行时性能。 - This is considered high and suggests that the system may be I/ O bound.
这被认为是相当高的，因而也就意味着系统可能是I/Obound。 - For example, reducing unnecessary code page conversion is not goign to help if your system is heavily I/ O bound due to an unfortunate table space configuration.
例如，如果由于表空间配置有问题，系统在I/O方面存在瓶颈，那么减少不必要的代码页转换仍然无济于事。 - For example, choosing a combination that is too I/ O bound can create poor results for the CPU, and vice versa.
例如，如果选择的组合过于受I/O所限，可能会导致CPU的测试结果不好，反之亦然。 - Many customers have high I/ O rates and are "I/ O bound" because of mail file sizes.
许多客户由于邮件过大而产生很高的I/O率和“I/O绑定”。 - If the slow operation is I/ O bound, you need to determine what part of the application is responsible for the I/ O.
如果操作缓慢是由于I/O所致，您需要判断是哪部分应用程序导致了I/O问题。 - The test site remains bottlenecked on the database server I/ O and bound by performance characteristics of the database server disk.
测试网站仍然遭遇数据库服务器I/O瓶颈，并受数据库服务器磁盘性能的限制。 - The next section shows some tools that help determine whether a task is CPU or I/ O bound.
下一节介绍了一些工具，可以帮助判定任务是受限于CPU还是I/O。 - To prevent threads from hogging the CPU, Linux dynamically raises or lowers a thread's priority based on factors such as whether the thread is I/ O or CPU bound.
为了防止线程霸占CPU，Linux根据一些因素（如线程是I/O限制还是CPU限制）动态提高或降低线程的优先级。 - It's possible that your system might actually be memory or I/ O bound and not CPU bound.
还有可能您的系统实际上是内存或I/O受限，而非CPU受限。 - The insertion process is essentially the I/ O bound for the database.
插入过程是数据库中实质上的I/O开销。 - This typically results in a significant decrease in elapsed time for I/ O bound queries, while incurring a minor increase in CPU time.
这通常可以显著减少I/Obound查询所需的时间，而代价只是稍微增加的CPU时间。 - Unless your XML inserts are heavily I/ O bound, the increased CPU consumption typically translates to reduced insert throughput.
除非XML插入中I/O占极大一部分，否则增加的CPU消耗通常会导致插入的吞吐量下降。 - CPUs are so much faster than physical disks that it is not uncommon to find poorly performing database servers that are significantly I/ O bound and underperforming by many times their true potential.
由于CPU比物理磁盘快得多，所以常常可以发现性能糟糕的数据库服务器，它们面临非常密集的I/O，表现出来的性能离它们的真正潜能差好多倍。 - Typically programs are either computation bound or I/ O bound and by using asynchronous workflows you will generally see improvements in both cases.
典型的程序不是在进行计算就是在进行I/O处理，通过利用异步工作流，你通常在这两个方面都能看到性能有所提升。 - Physical inputoutput function multitasking real-time I/ O bound process
实际输入-输出功能多任务实时输入输出联编处理过程 - Multitasking real-time I/ O bound process
多任务实时输入输出联编处理过程 - For worker threads, that purpose is to perform I/ O bound or other long tasks that are not directly related to the UI.
对于工作线程来说，这个效果是执行绑定的I/O，或者其他与用户界面直接相关的长时间任务。 - While not an issue for CPU-bound requests, requests that are I/ O bound can cause the server to run out of threads.
在CPU繁忙的请求不构成问题的情况下，I/O繁忙的请求也可能会让服务器陷于无线程可用的境地。 - I/ O requests bound for the LUNs ( logical units) are dispatched to parallel physical paths by the SPD driver to distribute the host load to the storage network.
将LUN的I/O请求分配到它的所有路径上，使主机的负载均匀地分布在存储网络中。